Date: Wed, 11 Dec 1996 22:33:27 GMT
Server: NCSA/1.5
Content-type: text/html
Last-modified: Sun, 01 Sep 1996 22:08:26 GMT
Content-length: 3266

<HTML>

<HEAD>
<TITLE>CS 302 Section 70 - Gradesheets</TITLE>
</HEAD>

<BODY>

<H2><!WA0><!WA0><!WA0><A HREF="http://www.cs.wisc.edu/~tick/cs302.html#assignments" ><!WA1><!WA1><!WA1><IMG SRC="http://www.cs.wisc.edu/~tick/icons/arrowleft.gif" WIDTH=15 HEIGHT=15></A> Gradesheets</H2>

<HR>

You will be given a gradesheet for each assignment showing the allocation of marks.  Please read it carefully to make sure you do everything that is required.  Some of the things it will include are:<P>
<DL>
   <DT>Test Data and Correct Output:
   <DD>The gradesheet may contain a list of test data that will be used to check that your program works correctly.  Make sure your program follows the assignment specifications and produces the required output.  Always run your program with the given test data and manually check your results for errors.  You must run your program with the test data given but also make sure it works for other valid data.  For some of the advanced programming assignments you will be asked to create your own test data.<P>

   <DT>User Interface:
   <DD>Provide meaningful prompts for the user when reading in values from the keyboard.  Display the results appropriately labelled so that they are easy to understand.<P>

   <DT>Correct use of FORTRAN statements:
   <DD>Use the most appropriate FORTRAN statement(s) to solve the problem.  Make sure these statements work for all possible valid input values.  Do not use any FORTRAN statements which we will not cover in class prior to the due date - if it hasn't been covered in class then you shouldn't use it in your program yet.<P>

   <DT>Indenting, neatness and variable names:
   <DD>All FORTRAN code should be written in uppercase letters.  Comments and documentation should be written in mixed case.  Leave blank lines between the major sections of your program.  Indent <TT>IF</TT> statements and <TT>DO</TT> loops three spaces.  Always try to use meaningful variable names of six or fewer characters.<P>

   <DT>Functions, subroutines and arguments:
   <DD>Use functions and subroutines to break down the problem into simpler sub-programs for clarity and efficiency.  Always use arguments to pass values into and out of functions and subroutines.  Do not use global referencing or <TT>COMMON</TT> blocks unless specifically asked to.<P>

   <DT>Flexible, modular, robust and efficient:
   <DD>Design your program so that it can be easily modified and enhanced.  Solve the problem in the most obvious and straight-forward manner.  Avoid writing redundant statements.  Do not include unnecessary statements but do not sacrifice clarity for efficiency.<P>

   <DT>Documentation:
   <DD>You must include comments in your program.  Explain what your program does, how to use it and how it works.  Describe <STRONG>all</STRONG> variable declarations.  Explain what the major sections of your program are and how they work.  Explain all functions and subroutines and their input and output arguments.  Explain any sections of code that are complex or tricky.<P>
</DL>

</BODY>

<HR>

<ADDRESS>
<H5>Copyright &copy 1996 Modified from <!WA2><!WA2><!WA2><A HREF="http://www.cs.wisc.edu/~bestor/bestor.html">Gareth S. Bestor</A> (<!WA3><!WA3><!WA3><A HREF="mailto:bestor@cs.wisc.edu">bestor@cs.wisc.edu</A>).  Last modified September 1, 1996.</H5>
</ADDRESS>

</HTML>
